home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950329-19950528
/
000470_news@columbia.edu_Sun May 28 22:41:43 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA11571
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Mon, 29 May 1995 07:37:26 -0400
Received: by apakabar.cc.columbia.edu id AA08488
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Mon, 29 May 1995 07:37:24 -0400
Path: news.columbia.edu!spcuna!solaris.cc.vt.edu!news.alpha.net!uwm.edu!spool.mu.edu!bloom-beacon.mit.edu!uhog.mit.edu!news.mtholyoke.edu!news.umass.edu!news.amherst.edu!not-for-mail
From: jwmanly@unix.amherst.edu (John W. Manly)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit under MS-Windows
Date: 28 May 1995 18:41:43 -0400
Organization: Amherst College, Amherst MA, USA
Lines: 24
Message-Id: <3qau77$d4g@amhux3.amherst.edu>
References: <3q04p0$1ldu@ns2-1.CC.Lehigh.EDU> <heliosD951IA.IC8@netcom.com> <1995May25.195311.52307@cc.usu.edu> <heliosD993n1.ML8@netcom.com>
Nntp-Posting-Host: amhux3.amherst.edu
X-Newsreader: TIN [version 1.2 PL0]
Apparently-To: kermit.misc@watsun.cc.columbia.edu
What we have diagnosed in this "unable to find hardware, using BIOS"
situation is that it's a timing related thing. If we try to access the port
via a SET PORT command or a CONNECT right after Kermit starts up, it fails
fairly reliably. But if we wait two or three seconds after Kermit starts,
the connection works just fine. It looks for all the world as if Windows
is just taking to long to "let go" of the serial port (or initialize its
emulation).
The really frustrating thing is that you can't just put a PAUSE or WAIT
command in the MSKERMIT.INI file to cause the necessary delay -- those
commands don't work either -- Kermit just zips by them as if they weren't
there during this period before the serial interface is enabled.
So what we finally did, for those machines where this happens (and it happens
by no means to all of them) is insert a "Press RETURN to continue" message
at the beginning of the MSKERMIT.INI file, which seems to provide enough time
for Windows to do whatever it needs to do for Kermit's SET PORT command to
work. I thought about just writing a counting loop, but decided it wasn't
worth the hassle since I would have to worry about the relative speed of
the machine to make sure it didn't take too long on slow machines, but didn't
complete too quickly (before SET PORT would work) for fast ones.
- John W. Manly <JWMANLY@AMHERST.EDU> Amherst College